[3.9] gh-97514: Don't use Linux abstract sockets for multiprocessing (GH-98501) ...
authorMiss Islington (bot) <31488909+miss-islington@users.noreply.github.com>
Fri, 28 Oct 2022 10:08:30 +0000 (03:08 -0700)
committerArnaud Rebillout <arnaudr@debian.org>
Tue, 14 Apr 2026 04:38:32 +0000 (11:38 +0700)
commit03d58246150a4cc4776e135c71721bb98e945a28
tree3de87dc7a888ff0245ab700ab842657e8ac9abcc
parent9fbab009c83ebb02f8ddb185b4ac0dff55015403
[3.9] gh-97514: Don't use Linux abstract sockets for multiprocessing (GH-98501) (#98504)

Linux abstract sockets are insecure as they lack any form of filesystem
permissions so their use allows anyone on the system to inject code into
the process.

This removes the default preference for abstract sockets in
multiprocessing introduced in Python 3.9+ via
https://github.com/python/cpython/pull/18866 while fixing
https://github.com/python/cpython/issues/84031.

Explicit use of an abstract socket by a user now generates a
RuntimeWarning.  If we choose to keep this warning, it should be
backported to the 3.7 and 3.8 branches.
(cherry picked from commit 49f61068f49747164988ffc5a442d2a63874fc17)

Co-authored-by: Gregory P. Smith <greg@krypto.org>
Gbp-Pq: Name 0010-3.9-gh-97514-Don-t-use-Linux-abstract-sockets-for-mu.patch
Lib/multiprocessing/connection.py